feat(snap-network-utils): add shared AssetsProvider (WPN-1784) - #82
feat(snap-network-utils): add shared AssetsProvider (WPN-1784)#82ulissesferreira wants to merge 1 commit into
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
All alerts resolved. Learn more about Socket for GitHub. This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring alerts on:
|
|
@SocketSecurity ignore npm/shiki@0.14.7 |
|
@SocketSecurity ignore npm/vscode-oniguruma@1.7.0 |
|
@SocketSecurity ignore npm/cjs-module-lexer@1.4.3 |
|
@SocketSecurity ignore npm/marked@4.3.0 |
|
@SocketSecurity ignore npm/@metamask/snaps-controllers@19.0.1 |
|
@SocketSecurity ignore npm/@metamask/assets-controller@11.2.0 |
|
@SocketSecurity ignore npm/@metamask/eth-json-rpc-infura@10.3.0 |
|
@SocketSecurity ignore npm/@metamask/assets-controllers@110.0.2 |
|
@SocketSecurity ignore npm/@metamask/multichain-network-controller@3.2.1 |
|
@SocketSecurity ignore npm/@ethersproject/providers@5.8.0 |
|
@SocketSecurity ignore npm/@metamask/network-controller@34.0.0 |
|
@SocketSecurity ignore npm/@metamask/config-registry-controller@1.0.0 |
|
@SocketSecurity ignore npm/@tanstack/query-core@5.101.4 |
|
@SocketSecurity ignore npm/@metamask/phishing-controller@17.3.0 |
|
@SocketSecurity ignore npm/@metamask/core-backend@7.0.0 |
|
@SocketSecurity ignore npm/keccak@3.0.4 |
|
@SocketSecurity ignore npm/@metamask/profile-sync-controller@28.3.0 |
|
@SocketSecurity ignore npm/@metamask/core-backend@8.0.0 |
|
@SocketSecurity ignore npm/ethereumjs-wallet@1.0.2 |
|
@SocketSecurity ignore npm/@metamask/remote-feature-flag-controller@4.2.2 |
|
@SocketSecurity ignore npm/rlp@2.2.7 |
|
@SocketSecurity ignore npm/@metamask/transaction-controller@69.3.0 |
|
@SocketSecurity ignore npm/ulid@2.4.0 |
|
@SocketSecurity ignore npm/ws@8.18.0 |
|
@SocketSecurity ignore npm/shiki@0.14.7 |
|
@SocketSecurity ignore npm/vscode-oniguruma@1.7.0 |
## Explanation <!-- Thanks for your contribution! Take a moment to answer these questions so that reviewers have the information they need to properly understand your changes: * What is the current state of things and why does it need to change? * What is the solution your changes offer and how does it work? * Are there any changes whose purpose might not obvious to those unfamiliar with the domain? * If your primary goal was to update one package but you found you had to update another one along the way, why did you do so? * If you had to upgrade a dependency, why did you do so? --> Proposal to simplify `AssetsService` types and returned values, to align it to what's currently returned by AssetsController's actions. ## References <!-- Are there any issues that this pull request is tied to? Are there other links that reviewers should consult to understand these changes better? Are there client or consumer pull requests to adopt any breaking changes? For example: * Fixes #12345 * Related to #67890 --> Related to #82 ## Checklist - [ ] I've updated the test suite for new or updated code as appropriate - [ ] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate - [ ] I've communicated my changes to consumers by [updating changelogs for packages I've changed](https://github.com/MetaMask/internal-snaps/tree/main/docs/processes/updating-changelogs.md) - [ ] I've introduced [breaking changes](https://github.com/MetaMask/internal-snaps/tree/main/docs/processes/breaking-changes.md) in this PR and have prepared draft pull requests for clients and consumer packages to resolve them
|
@SocketSecurity ignore npm/@metamask/assets-controller@13.0.0 |
|
@SocketSecurity ignore npm/@metamask/assets-controllers@110.0.3 |
|
@SocketSecurity ignore npm/@metamask/config-registry-controller@2.0.0 |
|
@SocketSecurity ignore npm/@metamask/core-backend@8.1.0 |
|
@SocketSecurity ignore npm/@metamask/geolocation-controller@1.0.0 |
|
@SocketSecurity ignore npm/@metamask/multichain-network-controller@3.2.2 |
|
@SocketSecurity ignore npm/@metamask/network-controller@35.0.0 |
|
@SocketSecurity ignore npm/@metamask/remote-feature-flag-controller@5.0.0 |
|
@SocketSecurity ignore npm/@metamask/transaction-controller@69.4.0 |
80f3343 to
0d6b38b
Compare
76d9473 to
f4e8722
Compare
8747d44 to
8589132
Compare
|
@metamaskbot publish-preview |
|
Preview builds have been published. Learn how to use preview builds in other projects. Expand for full list of packages and versions. |
Summary
AssetsProviderto@metamask/snap-networks-utilsas a thin, typed read layer over CoreAssetsController@metamask/assets-controllerto^13.0.0and wire messenger actions forgetAccountAssetByID,getAccountAssetsByIDs, andgetAccountAssetsByScopeAssetsProvider,AssetsProviderMessenger, andASSETS_PROVIDER_NAMEfrom the package rootsnap.manifest.jsonbundle shasums after lockfile changesTest plan
yarn workspace @metamask/snap-networks-utils run buildyarn workspace @metamask/snap-networks-utils run testyarn constraints